RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-31 07:52:55 +01:00
Code Issues Projects Releases Wiki Activity
ee0e14ab3f
llvm-mirror/test/Object/archive-update.test

38 lines
1.2 KiB
Plaintext
Raw Normal View History

Add a test for llvm-ar's u option. llvm-svn: 186192
2013-07-12 21:34:24 +02:00
Test the 'u' option of llvm-ar
REQUIRES: shell
RUN: cd %T
RUN: rm -f %t.a
Change archive-update.test to create a new file on the fly. llvm-svn: 186206
2013-07-12 23:17:17 +02:00
Create a file named evenlen that is newer than the evenlen on the source dir.
The archive update test has a subtle race condition in it: if the test is executed within the same second as the inputs for the test are checked out from the source tree, it will fail to update due to being below the resolution of the 'mtime' test used. Now, this may seem improbably to you... ok, maybe *really* improbable, but consider a system which does distributed execution of tests by shipping their inputs to another machine and runs them. That might cause the mtime to be quite recent during the test run. ;] Instead, create two files directly in the test (allowing all platforms to see the problem) and add either a use of the 'touch' command that forces one mtime to some time quite a bit in the past, or it sleeps for just over a second to be outside of the precision window. llvm-svn: 186282
2013-07-14 12:46:51 +02:00
RUN: mkdir -p %t.older
RUN: echo older > %t.older/evenlen
Either the shell supports the 'touch' command with a flag to manually set the
mtime or we sleep for over a second so that the mtime is definitely observable.
RUN: touch -m -t 200001010000 %t.older/evenlen || sleep 1.1
RUN: mkdir -p %t.newer
RUN: echo newer > %t.newer/evenlen
RUN: touch %t.newer/evenlen
Change archive-update.test to create a new file on the fly. llvm-svn: 186206
2013-07-12 23:17:17 +02:00
Add a test for llvm-ar's u option. llvm-svn: 186192
2013-07-12 21:34:24 +02:00
Create an achive with the newest file
The archive update test has a subtle race condition in it: if the test is executed within the same second as the inputs for the test are checked out from the source tree, it will fail to update due to being below the resolution of the 'mtime' test used. Now, this may seem improbably to you... ok, maybe *really* improbable, but consider a system which does distributed execution of tests by shipping their inputs to another machine and runs them. That might cause the mtime to be quite recent during the test run. ;] Instead, create two files directly in the test (allowing all platforms to see the problem) and add either a use of the 'touch' command that forces one mtime to some time quite a bit in the past, or it sleeps for just over a second to be outside of the precision window. llvm-svn: 186282
2013-07-14 12:46:51 +02:00
RUN: llvm-ar r %t.a %t.newer/evenlen
Add a test for llvm-ar's u option. llvm-svn: 186192
2013-07-12 21:34:24 +02:00
RUN: llvm-ar p %t.a | FileCheck --check-prefix=NEWER %s
Check that without the 'u' option the member is replaced with an older file.
The archive update test has a subtle race condition in it: if the test is executed within the same second as the inputs for the test are checked out from the source tree, it will fail to update due to being below the resolution of the 'mtime' test used. Now, this may seem improbably to you... ok, maybe *really* improbable, but consider a system which does distributed execution of tests by shipping their inputs to another machine and runs them. That might cause the mtime to be quite recent during the test run. ;] Instead, create two files directly in the test (allowing all platforms to see the problem) and add either a use of the 'touch' command that forces one mtime to some time quite a bit in the past, or it sleeps for just over a second to be outside of the precision window. llvm-svn: 186282
2013-07-14 12:46:51 +02:00
RUN: llvm-ar r %t.a %t.older/evenlen
Add a test for llvm-ar's u option. llvm-svn: 186192
2013-07-12 21:34:24 +02:00
RUN: llvm-ar p %t.a | FileCheck --check-prefix=OLDER %s
Check that with the 'u' option the member is replaced with a newer file.
The archive update test has a subtle race condition in it: if the test is executed within the same second as the inputs for the test are checked out from the source tree, it will fail to update due to being below the resolution of the 'mtime' test used. Now, this may seem improbably to you... ok, maybe *really* improbable, but consider a system which does distributed execution of tests by shipping their inputs to another machine and runs them. That might cause the mtime to be quite recent during the test run. ;] Instead, create two files directly in the test (allowing all platforms to see the problem) and add either a use of the 'touch' command that forces one mtime to some time quite a bit in the past, or it sleeps for just over a second to be outside of the precision window. llvm-svn: 186282
2013-07-14 12:46:51 +02:00
RUN: llvm-ar ru %t.a %t.newer/evenlen
Add a test for llvm-ar's u option. llvm-svn: 186192
2013-07-12 21:34:24 +02:00
RUN: llvm-ar p %t.a | FileCheck --check-prefix=NEWER %s
Check that with the 'u' option the member is not replaced with an older file.
The archive update test has a subtle race condition in it: if the test is executed within the same second as the inputs for the test are checked out from the source tree, it will fail to update due to being below the resolution of the 'mtime' test used. Now, this may seem improbably to you... ok, maybe *really* improbable, but consider a system which does distributed execution of tests by shipping their inputs to another machine and runs them. That might cause the mtime to be quite recent during the test run. ;] Instead, create two files directly in the test (allowing all platforms to see the problem) and add either a use of the 'touch' command that forces one mtime to some time quite a bit in the past, or it sleeps for just over a second to be outside of the precision window. llvm-svn: 186282
2013-07-14 12:46:51 +02:00
RUN: llvm-ar ru %t.a %t.older/evenlen
Add a test for llvm-ar's u option. llvm-svn: 186192
2013-07-12 21:34:24 +02:00
RUN: llvm-ar p %t.a | FileCheck --check-prefix=NEWER %s
NEWER: newer
The archive update test has a subtle race condition in it: if the test is executed within the same second as the inputs for the test are checked out from the source tree, it will fail to update due to being below the resolution of the 'mtime' test used. Now, this may seem improbably to you... ok, maybe *really* improbable, but consider a system which does distributed execution of tests by shipping their inputs to another machine and runs them. That might cause the mtime to be quite recent during the test run. ;] Instead, create two files directly in the test (allowing all platforms to see the problem) and add either a use of the 'touch' command that forces one mtime to some time quite a bit in the past, or it sleeps for just over a second to be outside of the precision window. llvm-svn: 186282
2013-07-14 12:46:51 +02:00
OLDER: older
Reference in New Issue Copy Permalink