Gradle / subprojects / core / src / integTest / groovy / org / gradle / api / internal

changedetection

Clone Tools

Stats

Commits this week: 0
Total Committers: 13
Last Commit:
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Wednesday 06 Sep 2017
2:36 am

Stefan Wolf

Polish test case

This makes the test fail on every second/third time or so.

Related issue: #2827

Options
    • -30
    • +35
    ./CorruptedTaskHistoryIntegrationTest.groovy
Tuesday 05 Sep 2017
3:22 pm

Stefan Wolf

Add more inputs to the task

This makes the test fail on every second/third time or so.

Options
    • -10
    • +30
    ./CorruptedTaskHistoryIntegrationTest.groovy
  2. … 1 more file in changeset.
2:30 pm

Stefan Wolf

Add a test for corrupted test

Options
    • -0
    • +108
    ./CorruptedTaskHistoryIntegrationTest.groovy
  2. … 1 more file in changeset.
Thursday 10 Aug 2017
10:05 am

Donát Csikós

On CI redirect maven central queries to local repo for integration tests

Options
    • -3
    • +1
    ./state/TaskTypeUpToDateIntegrationTest.groovy
  2. … 108 more files in changeset.
Tuesday 08 Aug 2017
10:25 am

Lóránt Pintér

Introduce `@ToBeImplemented` (#2643)

The `@ToBeImplemented` annotation replaces Groovy's `@NotYetImplemented`.

The problem with `NotYetImplemented` is that tests marked with it succeed no matter what causes the test to fail. Marked tests can pass because the expected failure is still present (which is the purpose of the test), or if the expected failure is replaced by some other failure.

It's better to write a test that explicitly tests for the expected failure, so when it fails for some other reason, it becomes noticeable. The purpose of the `@ToBeImplemented` annotation is to keep such tests easy to find in the code.

Options
    • -3
    • +4
    ./rules/OverlappingOutputsIntegrationTest.groovy
  2. … 9 more files in changeset.
Tuesday 25 Jul 2017
1:51 pm

Stefan Wolf

Simplify output file detection if there are no overlapping outputs (#2490)

If there are no overlapping outputs, we can just use all the declared

outputs as output files and do not need to filter since the task under

question has exclusive access to the directory/files.

We now ignore missing files in output properties, for these two ways

of snapshotting a directory (output file detection and regular snapshotting)

to be identical.

Options
    • -4
    • +0
    ./rules/OverlappingOutputsIntegrationTest.groovy
  2. … 40 more files in changeset.
Monday 08 May 2017
2:21 pm

Sterling Greene

Detect overlapping files for cacheable tasks

When two tasks overwrite one another, enforcing overlap detection doesn't

really make sense (because the outcome is the same).

But when two tasks append to a single output file, we should disable caching

because the order of the two tasks executing matters more.

+review REVIEW-6522

Options
    • -8
    • +8
    ./rules/OverlappingOutputsIntegrationTest.groovy
  2. … 3 more files in changeset.
Thursday 04 May 2017
8:40 am

Stefan Wolf

Extract test fixture for HttpBuildCache

Options
    • -2
    • +2
    ./rules/OverlappingOutputsIntegrationTest.groovy
  2. … 21 more files in changeset.
Thursday 06 Apr 2017
12:44 pm

Sterling Greene

Add more coverage for the mixed fileTask/dirTask overlapping output tests

+review REVIEW-6493

Options
    • -1
    • +11
    ./rules/OverlappingOutputsIntegrationTest.groovy
12:00 pm

Sterling Greene

Simplify overlapping output file integ test helper

+review REVIEW-6493

Options
    • -27
    • +14
    ./rules/OverlappingOutputsIntegrationTest.groovy
Wednesday 05 Apr 2017
1:50 pm

Sterling Greene

Add more reasoning for why we ignore directories when checking for overlaps

+review REVIEW-6493

Options
    • -0
    • +2
    ./rules/OverlappingOutputsIntegrationTest.groovy
  2. … 1 more file in changeset.
12:10 pm

Sterling Greene

Rework all of the overlapping tests to be more clear

+review REVIEW-6493

Options
    • -206
    • +275
    ./rules/OverlappingOutputsIntegrationTest.groovy
Friday 31 Mar 2017
2:19 pm

Sterling Greene

Detect overlapping inputs in a simple way

- Detect overlapping outputs after creating the "before execution" snapshot of outputs

- Add an OVERLAPPING_OUTPUTS caching reason

- Fix existing integration tests that are effected by overlapping outputs

+review REVIEW-6493

Options
    • -5
    • +14
    ./rules/OverlappingOutputsIntegrationTest.groovy
  2. … 13 more files in changeset.
Thursday 30 Mar 2017
3:15 pm

Sterling Greene

Add failing tests for overlapping outputs

+review REVIEW-6493

Options
    • -0
    • +482
    ./rules/OverlappingOutputsIntegrationTest.groovy
Monday 27 Feb 2017
9:21 pm

Adam Murdoch

Added special case handling for snapshots of values of array types, instead of snapshotting by serializing the entire array using Java serialization.

Options
    • -11
    • +14
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
    • -3
    • +6
    ./state/TaskEnumTypesInputPropertyIntegrationTest.groovy
  3. … 7 more files in changeset.
Friday 24 Feb 2017
6:55 pm

Adam Murdoch

Added special case handling for snapshots of values of type `Enum<?>` and `File`, instead of snapshotting by serializing the value using Java serialization.

Options
    • -0
    • +16
    ./state/TaskEnumTypesInputPropertyIntegrationTest.groovy
  2. … 8 more files in changeset.
4:56 pm

Adam Murdoch

Added special case handling for snapshots of values of type `Set<?>` and `Integer`, instead of snapshotting by serializing the value using Java serialization. This change also means we can handle a `Set` that contains values loaded from several different `ClassLoaders`.

Options
    • -2
    • +9
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
    • -2
    • +9
    ./state/TaskEnumTypesInputPropertyIntegrationTest.groovy
  3. … 10 more files in changeset.
3:25 pm

Adam Murdoch

Added some more test coverage for using `List` of various types for task input property values.

Options
    • -0
    • +72
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
    • -0
    • +76
    ./state/TaskEnumTypesInputPropertyIntegrationTest.groovy
  3. … 1 more file in changeset.
1:17 pm

Adam Murdoch

Added some test coverage to verify task is considered out of date when the type of an input property value changes.

Options
    • -1
    • +3
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
  2. … 1 more file in changeset.
1:55 am

Adam Murdoch

Changes to honor type's `equals()` method for task input property values. Also consider a value changed if the implementation classpath has changed since the previous execution.

Options
    • -6
    • +67
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
    • -2
    • +48
    ./state/TaskEnumTypesInputPropertyIntegrationTest.groovy
  3. … 12 more files in changeset.
Thursday 23 Feb 2017
11:41 pm

Adam Murdoch

Added some test coverage that the `equals()` method on a custom type is honored when checking task input property value for changes.

Options
    • -0
    • +65
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
  2. … 1 more file in changeset.
7:46 pm

Adam Murdoch

Introduced a type that represents a snapshot of the value of a task input property, used as part of the task history held in-memory and persisted to the file system.

This change introduces the type however for now the 'snapshot' simply a wrapper around the (potentially mutable) value.

Options
    • -20
    • +49
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
  2. … 10 more files in changeset.
6:12 pm

Adam Murdoch

Added a bunch more coverage for using custom types for task input properties.

Options
    • -0
    • +194
    ./state/TaskCustomTypesInputPropertyIntegrationTest.groovy
    • -13
    • +225
    ./state/TaskEnumTypesInputPropertyIntegrationTest.groovy
  3. … 2 more files in changeset.
Wednesday 28 Dec 2016
5:41 pm

Adam Murdoch

Removed some cases of messing with file timestamps in tests. These should not be required any more.

Options
    • -5
    • +0
    ./state/TaskTypeUpToDateIntegrationTest.groovy
  2. … 5 more files in changeset.
Monday 24 Oct 2016
3:54 pm

Adam Murdoch

Removed trace from int tests.

Options
    • -6
    • +0
    ./state/TaskTypeUpToDateIntegrationTest.groovy
  2. … 2 more files in changeset.
Monday 10 Oct 2016
5:10 am

Lari Hotari <lari.hotari@gradle.com>

Merge branch 'release'

Options
    • -3
    • +18
    ./state/TaskTypeUpToDateIntegrationTest.groovy
Sunday 09 Oct 2016
7:43 pm

Adam Murdoch

Added some trace to int test.

Options
    • -2
    • +12
    ./state/TaskTypeUpToDateIntegrationTest.groovy
5:14 pm

Adam Murdoch

Added some further trace to hunt down flaky test.

Options
    • -0
    • +2
    ./state/TaskTypeUpToDateIntegrationTest.groovy
  2. … 2 more files in changeset.
4:17 pm

Adam Murdoch

Added some diagnostics to flaky test.

Options
    • -1
    • +4
    ./state/TaskTypeUpToDateIntegrationTest.groovy
Thursday 06 Oct 2016
10:22 am

Stefan Wolf

Fix flakiness of TaskTypeUpToDateIntegrationTest

My theory is that the second run of the copy task after the

change was not up to date (that was the error reported in the

flaky tests) since when snapshotting the task outputs after the

second copy task given that the old output has been there before

the cache thinks that we do not need to snapshot since less a

second passed since the output file has been created. Then

we would record the output file with the state at the beginning

of the copy task and the second run would then mark it as

out of date since the output changed.

Options
    • -0
    • +10
    ./state/TaskTypeUpToDateIntegrationTest.groovy