use env files for github actions

[sriv]

No description provided.

[github-actions]

Benchmark Results

java_maven_multithreaded.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	183%	355184	0:23.08	0
c532320	183%	303728	0:22.61	0
c93f7af	153%	362648	0:37.51	0
9d74fa0	156%	344276	0:34.92	0

java_maven_parallel.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	184%	318832	0:21.98	0
c532320	184%	340820	0:20.92	0
c93f7af	158%	341744	0:31.93	0
9d74fa0	152%	285432	0:27.87	0

java_gradle_parallel.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	178%	394976	0:20.54	0
c532320	178%	374068	0:20.26	0
c93f7af	166%	639544	0:30.80	0
9d74fa0	180%	579480	0:37.62	0

java_gradle_serial.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	179%	388428	0:21.85	0
c532320	177%	349640	0:21.11	0
c93f7af	166%	619168	0:33.39	0
9d74fa0	180%	625256	0:37.16	0

java_simple_multithreaded.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	181%	397856	0:13.15	0
c532320	174%	384524	0:13.73	0
c93f7af	174%	385536	0:14.13	0
9d74fa0	168%	407176	0:12.53	0

java_gradle_multithreaded.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	180%	376804	0:18.33	0
c532320	182%	355644	0:20.04	0
c93f7af	179%	558492	0:33.83	0
9d74fa0	180%	614508	0:28.63	0

java_maven_serial.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	181%	318024	0:17.65	0
c532320	181%	338348	0:18.11	0
c93f7af	147%	296200	0:30.25	0
9d74fa0	146%	317672	0:27.38	0

java_simple_parallel.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	185%	316576	0:20.36	0
c532320	188%	316540	0:20.17	0
c93f7af	182%	324672	0:20.33	0
9d74fa0	169%	363620	0:23.73	0

java_simple_serial.csv

Commit	CPU	Memory	Time	ExitCode
6e0d83f	179%	351068	0:13.29	0
c532320	170%	343216	0:14.42	0
c93f7af	163%	341344	0:15.11	0
9d74fa0	154%	367236	0:18.24	0

Notes

• The results above are generated by running against seed projects in https://github.com/getgauge/gauge-benchmark
• These results are not persisted, but on merging to master the benchmark will be rerun.
• These benchmark are run in Github Actions' agents, which are virtualized. Results are not to be taken as actual benchmarks.Rather, these are indicative numbers and make sense for comparison.

---

See Workflow log for more details.

[zabil]

golangci-lint / lint is failing, maybe worth fixing those issues as a part of this PR too?

[sriv]

yes, am looking at those. I had to update the gh action for golang-ci lint and as part of that I updated the linter version, I guess new issues are reported (which is good).

fixing those.