UnitTestBot / UnitTestBot/usvm
Compilation errors in generated times, possible reasoned by incorrect types resolving in machine
Open
@Damtev is already working on this.
Since Nov 23, 2023.
bug
- Dominant language
- Kotlin
- Stars
- 33
- Forks
- 27
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 15
Description
Run ContestEstimator with the following options:
timeLimit = 120
methodFilter = "com.google.common.collect.MinMaxPriorityQueue.*"
projectFilter = listOf("guava")
NOTE that this problems does not reproduce each time. But sometimes...
Compilation errors: C:\UtBotJava\UTBotJava\utbot-junit-contest\build\output\test_candidates\guava\com\google\common\collect\MinMaxPriorityQueueTest.java:5118: error: no suitable method found for create(ServiceDefinitionImpl)
MinMaxPriorityQueue.create(serviceDefinitionImpl);
^
method MinMaxPriorityQueue.<E#1>create() is not applicable
(cannot infer type-variable(s) E#1
(actual and formal argument lists differ in length))
method MinMaxPriorityQueue.<E#2>create(Iterable<? extends E#2>) is not applicable
(inference variable E#2 has incompatible bounds
upper bounds: Comparable<E#2>
lower bounds: SDDocument)
where E#1,E#2 are type-variables:
E#1 extends Comparable<E#1> declared in method <E#1>create()
E#2 extends Comparable<E#2> declared in method <E#2>create(Iterable<? extends E#2>)
After quick analysis, it seems that the problem is not in compilation itself, but in the types produced by symbolic machine.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.