Python/pytest problemMatcher doesn't seem to work? #25393

billyvg · 2020-05-27T04:54:31Z

billyvg
May 27, 2020

I’m trying to use the problemMatch defined here in actions/setup-python: https://github.com/actions/setup-python/blob/807b74f98ca701f414ddaa8a4187e7cffa93cbbd/.github/python.json

It doesn’t seem to work, you can see the log output here: https://github.com/getsentry/sentry/pull/19038/checks?check_run_id=711757943#step:21:130

In that PR I’ve also tried with a different matcher (which doesn’t work either): https://github.com/getsentry/sentry/pull/19038/files#diff-8aa942dcc12e296fcb1cbf95181de009R7

Testing the patterns in javascript with new RegExp() seem to work fine, however.

Answered by BrightRan

May 27, 2020

@billyvg,
Maybe you can try to reference the below file in actions/setup-python to add-matcher:

github.com

actions/setup-python/blob/807b74f98ca701f414ddaa8a4187e7cffa93cbbd/src/setup-python.ts

import * as core from '@actions/core';
import * as finder from './find-python';
import * as path from 'path';
import * as os from 'os';
async function run() {

try {

let version = core.getInput('python-version');

if (version) {

const arch: string = core.getInput('architecture') || os.arch();

const installed = await finder.findPythonVersion(version, arch);

core.info(Successfully setup ${installed.impl} (${installed.version}));

}

const matchersPath = path.join(__dirname, '..', '.github');

core.info(#…

View full answer

BrightRan · 2020-05-27T07:43:29Z

BrightRan
May 27, 2020

@billyvg,
Maybe you can try to reference the below file in actions/setup-python to add-matcher:

github.com

actions/setup-python/blob/807b74f98ca701f414ddaa8a4187e7cffa93cbbd/src/setup-python.ts

import * as core from '@actions/core';
import * as finder from './find-python';
import * as path from 'path';
import * as os from 'os';
async function run() {

try {

let version = core.getInput('python-version');

if (version) {

const arch: string = core.getInput('architecture') || os.arch();

const installed = await finder.findPythonVersion(version, arch);

core.info(Successfully setup ${installed.impl} (${installed.version}));

}

const matchersPath = path.join(__dirname, '..', '.github');

core.info(##[add-matcher]${path.join(matchersPath, 'python.json')});

} catch (err) {

core.setFailed(err.message);

}

}

This file has been truncated. show original

0 replies

billyvg · 2020-06-01T22:34:41Z

billyvg
Jun 1, 2020
Author

@brightran Right, so by using actions/setup-python we should have that matcher added, correct? Now that I’m looking at the log output again, I’m not so sure if the 2nd matcher works

0 replies

BrightRan · 2020-06-02T02:23:45Z

BrightRan
Jun 2, 2020

@billyvg,
> so by using actions/setup-python we should have that matcher added, correct?
Yes, I think that’s it.

> I’m not so sure if the 2nd matcher works
According to the description from the docs about Problem Matchers (see here),

Registering two problem-matchers with the same owner will result in only the problem matcher registered last running.

if you add another Problem Matchers (using the ::add-matcher:: command) after executing the setup-python action in your workflow, the new Problem Matchers should become the only Problem Matchers in work.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Python/pytest problemMatcher doesn't seem to work? #25393

{{title}}

Replies: 3 comments

{{title}}

{{title}}

{{title}}

Select a reply

GitHub Community

Python/pytest problemMatcher doesn't seem to work? #25393

billyvg May 27, 2020

actions/setup-python/blob/807b74f98ca701f414ddaa8a4187e7cffa93cbbd/src/setup-python.ts

Replies: 3 comments

BrightRan May 27, 2020

actions/setup-python/blob/807b74f98ca701f414ddaa8a4187e7cffa93cbbd/src/setup-python.ts

billyvg Jun 1, 2020 Author

BrightRan Jun 2, 2020

billyvg
May 27, 2020

BrightRan
May 27, 2020

billyvg
Jun 1, 2020
Author

BrightRan
Jun 2, 2020